home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / Xm / MrmRegisterNames.z / MrmRegisterNames
Text File  |  1998-10-30  |  7KB  |  133 lines
  1.  
  2.  
  3.  
  4.      MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss((((3333XXXX))))      UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV      MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss((((3333XXXX))))
  5.  
  6.  
  7.  
  8.      NNNNAAAAMMMMEEEE
  9.           MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss - Registers the values associated with the
  10.           names referenced in UIL (for example, UIL callback function
  11.           names or UIL identifier names)
  12.  
  13.      SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  14.           #include <Mrm/MrmPublic.h>
  15.           CCCCaaaarrrrddddiiiinnnnaaaallll MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss(
  16.           MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrAAAArrrrgggglllliiiisssstttt rrrreeeeggggiiiisssstttteeeerrrr____lllliiiisssstttt,
  17.           MMMMrrrrmmmmCCCCoooouuuunnnntttt rrrreeeeggggiiiisssstttteeeerrrr____ccccoooouuuunnnntttt);
  18.  
  19.      VVVVEEEERRRRSSSSIIIIOOOONNNN
  20.           This page documents Motif 2.1.
  21.  
  22.      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  23.           The MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessssfunction registers a vector of names and
  24.           associated values for access in MRM.  The values can be
  25.           callback functions, pointers to user-defined data, or any
  26.           other values.  The information provided is used to resolve
  27.           symbolic references occurring in UID files to their run-time
  28.           values.  For callbacks, this information provides the
  29.           procedure address required by the Motif Toolkit.  For names
  30.           used as identifiers in UIL, this information provides any
  31.           run-time mapping the application needs.
  32.  
  33.           This function is similar to MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessssIIIInnnnHHHHiiiieeeerrrraaaarrrrcccchhhhyyyy,
  34.           except that the scope of the names registered by
  35.           MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessssIIIInnnnHHHHiiiieeeerrrraaaarrrrcccchhhhyyyyis limited to the hierarchy
  36.           specified in the call to that function, whereas the names
  37.           registered by MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeesssshave global scope.  When MRM
  38.           looks up a name, it first tries to find the name among those
  39.           registered for the given hierarchy.  If that lookup fails,
  40.           it tries to find the name among those registered globally.
  41.  
  42.           _r_e_g_i_s_t_e_r__l_i_s_t
  43.                     Specifies a list of name/value pairs for the names
  44.                     to be registered.  Each name is a case-sensitive,
  45.                     NULL-terminated ASCII string.  Each value is a
  46.                     32-bit quantity, interpreted as a procedure
  47.                     address if the name is a callback function, and
  48.                     uninterpreted otherwise.
  49.  
  50.           _r_e_g_i_s_t_e_r__c_o_u_n_t
  51.                     Specifies the number of entries in _r_e_g_i_s_t_e_r__l_i_s_t.
  52.  
  53.           The names in the list are case-sensitive.  The list can be
  54.           either ordered or unordered.
  55.  
  56.           Callback functions registered through MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeesssscan be
  57.           either regular or creation callbacks.  Regular callbacks
  58.           have declarations determined by Motif Toolkit and user
  59.           requirements.  Creation callbacks have the same format as
  60.  
  61.  
  62.  
  63.      Page 1                                         (printed 10/24/98)
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.      MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss((((3333XXXX))))      UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV      MMMMrrrrmmmmRRRReeeeggggiiiisssstttteeeerrrrNNNNaaaammmmeeeessss((((3333XXXX))))
  71.  
  72.  
  73.  
  74.           any other callback:
  75.  
  76.           vvvvooooiiiidddd CCCCaaaallllllllBBBBaaaacccckkkkPPPPrrrroooocccc(
  77.           WWWWiiiiddddggggeeeetttt ****wwwwiiiiddddggggeeeetttt____iiiidddd,
  78.           OOOOppppaaaaqqqquuuueeee ttttaaaagggg,
  79.           XXXXmmmmAAAAnnnnyyyyCCCCaaaallllllllbbbbaaaacccckkkkSSSSttttrrrruuuucccctttt ****ccccaaaallllllllbbbbaaaacccckkkk____ddddaaaattttaaaa);
  80.  
  81.           _w_i_d_g_e_t__i_d Specifies the widget ID associated with the widget
  82.                     performing the callback (as in any callback
  83.                     function).
  84.  
  85.           _t_a_g       Specifies the tag value (as in any callback
  86.                     function).
  87.  
  88.           _c_a_l_l_b_a_c_k__d_a_t_a
  89.                     Specifies a widget-specific data structure.  This
  90.                     data structure has a minimum of two members: event
  91.                     and reason.  The reason member is always set to
  92.                     MMMMrrrrmmmmCCCCRRRR____CCCCRRRREEEEAAAATTTTEEEE.
  93.  
  94.           Note that the widget name and parent are available from the
  95.           widget record accessible through _w_i_d_g_e_t__i_d.
  96.  
  97.      RRRREEEETTTTUUUURRRRNNNN
  98.           This function returns one of the following status return
  99.           constants:
  100.  
  101.           MMMMrrrrmmmmSSSSUUUUCCCCCCCCEEEESSSSSSSS
  102.                     The function executed successfully.
  103.  
  104.           MMMMrrrrmmmmFFFFAAAAIIIILLLLUUUURRRREEEE
  105.                     The function failed.
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.      Page 2                                         (printed 10/24/98)
  130.  
  131.  
  132.  
  133.